Use #import instead of @import #246
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Excellent point. Thank you for the pull request. |
|
Now published in version 2.1.2 |
msun
pushed a commit
to mindsnacks/appirater
that referenced
this pull request
Jan 11, 2017
Use #import instead of @import
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had issues using the current version of Appriater, as it would have required me to set the
CLANG_ENABLE_MODULESsetting toYES, which resulted in conflicts with other imports of C classes.As the source of Appirater is Objective-C anyways, and a CocoaPod should not have to require specific build settings of its target, I think using the old import notation is the better solution.